HADOOP-19105. Improve resilience in vector reads.#7105
HADOOP-19105. Improve resilience in vector reads.#7105steveloughran wants to merge 7 commits intoapache:trunkfrom
Conversation
Add a new releaser method, which then is invoked to release buffers on failure. It is a bit contrived how we try not break external implementations when adding a new default implementation to PositionedReadable: the releaser will be lost unless they do so. Change-Id: Ie2f95a89cfa79d3fdf33c1cc58f63e4ca00c6207
|
💔 -1 overall
This message was automatically generated. |
Trying to implement resilience in the s3a input stream; buffers of incomplete reads are now released on failures. Change-Id: I4b23c6a2ff417687fd19c1e8e9feef6cf733c031
Trying to implement resilience in the s3a input stream; buffers of incomplete reads are now released on failures. Change-Id: I851779383f8d120fe42bc97c5e6ae533c5fe2e23
|
💔 -1 overall
This message was automatically generated. |
Now: how do I pull this out so it can be used with the prefetch stream? Change-Id: I98e350ab3b28d9adc7b458dee4ceee56a0562f17
|
💔 -1 overall
This message was automatically generated. |
Conflicts: hadoop-tools/hadoop-aws/src/main/java/org/apache/hadoop/fs/s3a/S3AInputStream.java Change-Id: I46473271c9fdc9c5b3bbc561ecdc0a4ea36988ce
Change-Id: I669d2bf55795a091c0d2a3b54a11cd85dc2cee1c
|
💔 -1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
this is really complicated
|
|
💔 -1 overall
This message was automatically generated. |
Rigorous aborting of streams where appropriate, and if one range read fails in the fallback sequential read, so do all the others. factor out start/stop. This is preparing to pull this into a superclass so that all s3a streams get it. Change-Id: I8961d6737764bb696aa45338bb0300b2f6efeec6
01b4219 to
e11b0a9
Compare
|
💔 -1 overall
This message was automatically generated. |
|
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable. |
Add a new releaser method, which then is invoked to release buffers on failure.
It is a bit contrived how we try not break external implementations when adding a new default implementation to PositionedReadable: the releaser will be lost unless they do so.
For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles?